KYP — Know Your Process

Foundation Layer · Process Examination Protocol

Use this page to explain how your business process works.

You tell KOET how your business operates. KOET structures the information for continuous improvement.

✓ Housekeeping process
✓ Inventory process
✓ Customer onboarding process
✓ Construction workflow
✓ Salon operations

DO NOT use this page to record inventory or daily events.

Use Inventory or Daily Log instead.

Foundation Layer

Before KOET can improve a process, it must first know the process.

A doctor cannot prescribe without examining. Complete the six data layers below to build your AS-IS process and generate the Universal Swimlane — the primary diagnostic instrument of KOET.

Layer A Process Identity What is this process and what does it produce? ▶

Process Name *

Process Category

Process Owner Role

Department / Area / Location

Process Frequency

Process Criticality

Process Trigger — What starts this process? Terminal Output — What does this process deliver when complete? Customer of the Process — Who receives the output?

Layer B Actor Registry Who is involved? — becomes the swimlane rows ▶

Each actor becomes a lane in the swimlane. Add every role, team, or system involved — including customers or external parties that participate in the process.

Layer C Step Inventory What happens, in what order, and who does it? ▶

Add every step in sequence. Each step needs an owner from the Actor Registry. The more detail here — especially standards — the stronger the diagnostic output.

Layer D Flow Logic How does the process branch, loop, and end? ▶

Decision Paths — Where does the process branch based on a condition? Parallel Paths — Which steps can happen simultaneously? Re-entry / Rework Loops — Where does the process loop back? Terminal Point — How does the process end?

Layer E Standards & Quality Anchors What does good look like at the process level? ▶

Step-level standards are captured in Layer C. Use this section for process-level quality anchors and sign-off requirements.

Overall Acceptance Criteria — What does a successful run look like?

Sign-off Required?

Sign-off Role

Documentation Required at Process Completion

Layer F Time Architecture How long should this take, and what happens if delayed? ▶

Fixed Start Time (if applicable)

Total Expected Cycle Time (minutes)

Est. Wait / Idle Time (minutes)

Est. Value-Added Time (minutes)

SLA / Deadline Consequence of Delay

Choose a Process

Select your business type to get started

💡 To load a previously saved process, go to Export → Open Another Process and paste your file.

Process Details

—

Process Name

Status

Emoji

Process Category

▶ Version Control & Change Notes

Version (auto-increments on save)

Last Updated By

Batch ID Pattern

Change Notes

Ownership

Process Owner

Approval Owner

Backup Approver

Process Trigger

Trigger Type

Trigger Level

Role Management

Assigned persons & rotation partners

⚠️ Role IDs are locked and cannot be changed. Edit assigned persons, titles, and notes only.

Phases & Steps

Phase names are locked · Steps are editable

Gates

Gate IDs are locked · Questions and conditions are editable

⚠️ Gate IDs are locked. Edit gate questions, conditions, and approvers only.

QC Checks

Phase 4 · Approval & Storage

Daily Log Config

Drives daily log form generation

Non-Negotiable Rules

Critical warnings that block progression

Swimlane Preview

Generated from current JSON state

Click Regenerate to render the swimlane from the current process state.

QC Checklist

Generated from current process state

Click Regenerate to render the QC Checklist from the current process state.

Daily Log

Generated from current process state

Click Regenerate to render the Daily Log form from the current process state.

Training View

Generated from current process state

Click Regenerate to render the Training Guide from the current process state.

Version History

Management-only audit trail

Export & Manage

Save, download, and open processes

💡 Workflow: Edit your process → Save Version → use Generate Views (sidebar) to produce Swimlane, QC Checklist, Daily Log, and Training views directly. Download the Master Process File to keep a portable backup.

💾 Save Version

Increments the version number, records your change notes, and saves to this browser. Do this after every edit session.

📄 Download Master Process File

Downloads the full editable file — includes all version history, daily log config, QC checks, and roles. This is your master record. Keep it safe.

📥 HTML Snapshots

Download standalone HTML files for any view. These are shareable and work offline.

⚙️ Legacy: Static JSON Export

Produces a flattened static JSON for external integrations. Not required for normal use — the Generate Views section renders directly from your master file.

📋 Open Another Process

Paste any Master Process File here to open it in the editor. Works with all six current processes.

Intake Routes

Capture a process before entering it into KYP

KYP Doctrine — How Does This Work Today?

Before KOET can improve a process, it must first understand the process.

The 11 diagnostic questions KOET uses to build a complete AS-IS picture:

What is this process? (Name it)
What starts it? (Trigger)
What does it produce? (Output)
Who receives the output? (Customer / next step)
Who does what? (Actors and roles)
What are the steps, in what order? (Step inventory)
Where are the decision points? (Flow logic)
What does "done correctly" look like at each step? (Standards)
How long should this take? (Time architecture)
What could go wrong, and what happens when it does? (Failure modes)
Who signs off that it happened? (Accountability)

Intake Workflow

1

Raw Intake

→

2

Structured Draft

→

3

Human Review

→

4

Save Into KYP

→

5

Generate Outputs

Industry Context — optional but recommended

Industry

Operation Area

📋 Route 1 — Guided Intake

📄 Route 2 — Paste Raw Text

Answer these plain questions. No KOET knowledge required. Works for staff, clients, or managers.

Process Identity

1. What is the name of this process? *

2. Where does this process happen?

3. What causes this process to start?

4. What is produced or completed when it is done?

5. Who receives what is produced?

People & Steps

6. Who is involved in this process? (list roles or names) 7. Describe the main steps in order (can be rough, one per line)

Logic, Quality & Accountability

8. Are there any decision points where something different happens?

9. What does "done correctly" look like?

10. How long does this normally take?

11. Who approves or signs off when the process is done?

12. What is the most common problem in this process?

Engine Readiness

Downstream engines — what your current process data can power

Each engine requires specific data from your process file. Green = ready to generate. Amber = partial data. Red = data missing.